What/Why/How?

Fix handling of description/summary when they are $ref siblings next to a schema $ref so they resolve correctly and override the target schemas.

Why: Previously, bundling left description as a $ref object when used alongside another $ref, matching the bug described in the linked issue.

# openapi.yaml
openapi: 3.1.0
paths:
  /test:
    get:
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
                properties:
                  field:
                    description:
                      $ref: './components/schemas/description.md'
                    $ref: '#/components/schemas/Child'

components:
  schemas:
    Child:
      type: object
      properties:
        name:
          type: string

Reference

Fixes: СLI issue #1907

Testing

• Added unit and e2e tests
• Existing suites pass locally.

Screenshots (optional)

Check yourself

• Code changed? - Tested with Redoc/Realm/Reunite (internal)
• All new/updated code is covered by tests
• New package installed? - Tested in different environments (browser/node)
• Documentation update considered

Security

• The security impact of the change has been considered
• Code follows company security practices and guidelines